Information processing apparatus

ABSTRACT

An information processing apparatus includes: a creating unit that creates, from a first application deletable by a person with a first authority, a second application deletable by a person with a second authority; and a deleting unit that deletes the second application according to a predetermined condition when the first application is deleted.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on and claims priority under 35 USC 119 fromJapanese Patent Application No. 2018-087008 filed Apr. 27, 2018 andJapanese Patent Application No. 2018-075196 filed Apr. 10, 2018.

BACKGROUND (i) Technical Field

The present disclosure relates to an information processing apparatus.

(ii) Related Art

There has recently been proposed an information processing system inwhich data managed in a public DB may be customized and used by using aprivate DB (see, e.g., JP-A-2008-158816).

The information processing system disclosed in JP-A-2008-158816includes: a public DB for which a data rewriting by a general user isrestricted, and, for example, a data update is performed by anadministrator; a private DB for which data rewriting is allowed for thegeneral user; and a DB interface that performs various processings onthe public DB and the private DB based on a request from theadministrator or the general user. When the administrator requests theDB interface to delete data on the public DB, data of the private DBcorresponding to DB association information on the private DB isdeleted.

SUMMARY

Aspects of non-limiting embodiments of the present disclosure relate toproviding an information processing apparatus that makes it possible todelete a second application according to the intention of a person witha specific authority when the second application is created for use by aperson other than the person with the specific authority from a firstapplication published by the person with the specific authority.

Aspects of non-limiting embodiments of the present disclosure alsorelate to providing an information processing apparatus that makes itpossible to limit, for each item, change of setting values of a secondapplication by users when a first application available for pluralusers, in which setting values of setting items are registered, iscopied to create the second application in such a manner that it isavailable only for the users.

According to an aspect of the present disclosure, there is provided aninformation processing apparatus including: a creating unit that createsa second application that can be deleted by a person with a secondauthority, from a first application that can be deleted by a person witha first authority; and a deleting unit that deletes the secondapplication according to a predetermined condition when the firstapplication is deleted.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the present disclosure will be described indetail based on the following figures, wherein:

FIG. 1 is a block diagram illustrating an example of a control system ofan image forming apparatus according to an exemplary embodiment of thepresent disclosure;

FIG. 2 is a view illustrating an example of an app use control table;

FIG. 3 is a view illustrating an example of a public app managementtable;

FIG. 4A is a view illustrating an example of a private app managementtable for Mr. A, and FIG. 4B is a view illustrating an example of aprivate app management table for Mr. B;

FIG. 5A is a view illustrating an example of a screen management tablefor Mr. A, and FIG. 5B is a view illustrating an example of a screenmanagement table for Mr. B;

FIG. 6A is a view illustrating an example of a menu screen displayed forMr. A, and FIG. 6B is a view illustrating an example of a menu screendisplayed for Mr. B;

FIG. 7 is a flowchart illustrating an example of a creation flow of apublic application;

FIG. 8 is a flowchart illustrating an example of a copy flow of a publicapplication;

FIG. 9 is a flowchart illustrating an example of a deletion flow of apublic application;

FIG. 10 is a flowchart illustrating an example of a use flow of aprivate application of each user;

FIGS. 11A to 11C are views illustrating an example of an icon in a firstmodification;

FIGS. 12A and 12B illustrate another example of the app use controltable in a second modification, in which FIG. 12A is a view illustratingan example of the app use control table, and FIG. 12B is a viewillustrating an example of a permission table;

FIG. 13 is a view illustrating another example of the app use controltable in a third modification;

FIGS. 14A to 14D are views for explaining another example of the publicapp management table in a fourth modification;

FIG. 15 is a block diagram illustrating an example of a control systemof an image forming apparatus according to an exemplary embodiment ofthe present disclosure;

FIGS. 16A to 16C are views for explaining setting information held inapplications, in which FIG. 16A is a view illustrating an example ofsetting information before setting values of a public app are changed,FIG. 16B is a view illustrating an example of setting information afterthe setting values of the public app are changed, and FIG. 16C is a viewillustrating an example of setting information of the private app;

FIG. 17 is a flowchart illustrating an example of a creation flow of apublic app and a private app;

FIG. 18 is a flowchart illustrating an example of flow of change of asetting value of the private app;

FIG. 19 is a flowchart illustrating an example of a flow of change of asetting value of the public app; and

FIG. 20 is a flowchart illustrating an example of a flow at the time ofactivation of the private app after a setting value of the public app ischanged.

DETAILED DESCRIPTION

Hereinafter, exemplary embodiments of the present disclosure will bedescribed with reference to the accompanying drawings. In the respectivedrawings, constituent elements having substantially the same functionswill be denoted by the same reference numerals, and overlappingexplanations thereof will be omitted.

Summary of Exemplary Embodiment

An information processing apparatus according to an exemplary embodimentof the present disclosure includes: a creating unit that creates, from afirst application deletable by a person with a first authority, a secondapplication deletable by a person with a second authority; and adeleting unit that deletes the second application according to apredetermined condition when the first application is deleted.

The “person with the first authority” is, for example, an administratorwho manages a corresponding information processing apparatus or a systemincluding the corresponding information processing apparatus. The“person with the second authority” is, for example, a user other thanthe administrator.

The first application and the second application execute processingsspecified according to setting values of registered setting items. Asthe first application and the second application, for example, someapplications are immediately executed without displaying of a screen forconfirming setting values, and other applications are executed after ascreen for confirming setting values is displayed and confirmed.

The information processing apparatus may be, for example, an imageforming apparatus such as a multifunction machine or a facsimile device,a multifunctional mobile phone (smart phone), a personal computer (PC),or a tablet terminal.

Exemplary Embodiment

FIG. 1 is a block diagram illustrating an example of a control system ofan image forming apparatus according to an exemplary embodiment of thepresent disclosure; The image forming apparatus 1 is a multifunctionmachine having plural functions such as, for example, scanning,printing, copying, e-mailing, or facsimiling. The image formingapparatus 1 includes a controller 20, a storage 21, an operation display22, an image reading unit 23, an image forming unit 24, and acommunication unit 25. The multifunction machine is an example of aninformation processing apparatus.

The controller 20 is constituted by, for example, a central processingunit (CPU) and an interface. The CPU operates in accordance with aninformation processing program 210 to function as a receiving unit 200,a first creating unit 201, a second creating unit 202, a deleting unit203, a display controller 204, or an execution unit 205 or the like.Details of each of the units 200 to 205 will be described herein below.

The storage 21 is constituted by, for example, a read only memory (ROM),a random access memory (RAM), and a hard disk, and stores various typesof information including the information processing program 210, apublic app storage 211, private app storages 212A, 212B, . . .(hereinafter, these may also be collectively referred to as “private appstorage 212”) provided for each user, an app use control table 213, apublic app management table 214, private app management tables 215A,215B, . . . (hereinafter, these may also be collectively referred to as“private app management table 215”) provided for each user, and screenmanagement tables 216A, 216B, . . . (hereinafter, these may also becollectively referred to as “screen management table 216”) provided foreach user. The present specification uses “record” or “register” in acase where information is recorded to a table, and uses “store” in acase where information is recorded to a storage. Here, the user is anexample of a user excluding an administrator. When both theadministrator and the user are included, the administrator and the userare also called operators. The administrator is an example of a personwith a first authority. The user is an example of a person with a secondauthority. The private app storage 212 is an example of a storage area.

The public app storage 211 stores a public application (hereinafter,also simply referred to as a “public app”). FIG. 1 illustrates a statewhere the public app storage 211 stores public apps having, for example,app names of “two copies” and “send to Mr. C.” The public application isan example of a first application.

Here, the app name “two copies” indicates an application by which twocopies of a document with one or more pages are made. The app name “sendto Mr. C” indicates an application by which an image is sent to a userterminal device of Mr. C via an e-mail.

The private app storage 212 stores a private application (hereinafter,also simply referred to as a “private app”). FIG. 1 illustrates a statewhere the private app storage 212A for Mr. A stores private apps having,for example, app names of “copy in black/white” and “two copies.” Also,FIG. 1 illustrates a state where the private app storage 212B for Mr. Bstores private apps having, for example, app names of “send to Mr. A”and “send to Mr. C in color.” Hereinafter, the public app and theprivate app may be collectively and simply referred to as “apps.” Theprivate application is an example of a second application.

Here, the app name “copy in black/white” indicates an application bywhich an image read from a document is copied with a black-white image.The app name “send to Mr. A” indicates an application by which an imageis sent to a user terminal device of Mr. A via an e-mail. The app name“send to Mr. C in color” indicates an application by which a color imageis sent to a user terminal device of Mr. C via an e-mail.

The public app management table 214 is used for managing a public app.The private app management table 215 is used for managing a private appfor each user. The screen management table 216 is used for managing ascreen operated by a user, for each user.

In FIG. 1, it is assumed that the private app storage 212A, the privateapp management table 215A, and the screen management table 216A areprepared for Mr. A as a user, and the private app storage 212B, theprivate app management table 215B, and the screen management table 216Bare prepared for Mr. B as a user.

The “public application” is an application published by anadministrator, and only the administrator has an authority to performcreation and deletion. The private application is an application createdfor each user. The “private application” is an application obtained byduplicating the public application by an administrator or a user, whichis not open to others than the corresponding user. Only thecorresponding user has an authority to delete the private application.In the present specification, “copy” indicates that the privateapplication is created while setting values held in the publicapplication are kept as they are.

As for the public application and the private application, for example,some applications may be immediately executed without displaying of ascreen for confirming setting values, and other applications may beexecuted after a screen for confirming setting values is displayed andconfirmed.

The operation display 22 has a touch panel display having a touch panelsuperimposed on a display portion such as a liquid crystal display,which displays a screen such as a menu screen on the display portion,and accepts an operation from an operator to the touch panel. On themenu screen, an icon including an app name is displayed. When the iconis selected, the corresponding application is activated. The icon is onethat indicates a function of a processing to be executed by anapplication, on a display screen through, for example, pictures,pictograms, or letters, so as to instruct the processing to be executed.The icon is an example of an instruction unit.

The image reading unit 23 includes an automatic document feeder providedon a document table, and a scanner that reads image data from a documentplaced on the document table, or a document fed by the automaticdocument feeder. The image reading unit 23 stores the read image data inthe storage 21.

The image forming unit 24 forms a black-white image or a color image ona recording medium such as a sheet through, for example, anelectrophotographic system or an inkjet method.

The communication unit 25 transmits and receives information to/from anexternal device such as an administrator terminal device used by anadministrator and a user terminal device used by a user via a networkby, for example, an e-mail or a facsimile. The network is acommunication network such as a local network (LAN), the Internet, or apublic network, which transmits and receives data through, for example,a wired communication, a wireless communication or the like.

Configuration of App Use Control Table

FIG. 2 is a view illustrating an example of the app use control table213. The app use control table 213 is used when an administrator or auser registers a usage condition of a public app or a private app. Theapp use control table 213 includes items, such as, a “control ID” inwhich a control ID that identifies an app usage control is registered, a“usage condition” in which a usage condition of the app usage control isregistered, and a “registrant” in which a registrant name is registered.Here, the app usage control indicates a processing that grants a usagecondition of an app within the public app storage 211 and the privateapp storage 212. In the item of the “registrant” of FIG. 2, it isassumed that Z indicates an administrator name, and others, that is, Aand B, indicate user names.

A usage condition of a control ID “CON1” indicates that a control isperformed such that during a period when a public app is stored in thepublic app storage 211, a corresponding private app stored in theprivate app storage 212 may be used, and when the public app is deletedfrom the public app storage 211, the corresponding private app isdeleted from the private app storage 212. The private app correspondingto the public app is an app obtained by duplicating the public app. Ingeneral, app names are the same, but a part of setting values may bechanged, and then, an app with a changed app name may be included.

A usage condition of a control ID “CON2” allows a private app to beusable a designated number of times, which indicates a processing inwhich a user may use the private app the designated number of times, andthe private app is deleted after the designated number of times. Thecorresponding drawing indicates an example in which “usable once” isregistered in the usage condition of “CON2.”

Usage conditions of control IDs “CON3” and “CON4” allow a private app tobe usable for a designated period, which indicates a processing in whicha user may use the private app during the designated period, and theprivate app is deleted after the designated period. The correspondingdrawing indicates an example in which “usable until 2018/12/1” isregistered in the usage condition of “CON3,” and “usable until2019/3/31” is registered in the usage condition of “CON4.”

Although not described in FIG. 2, as a usage condition of a control ID“CONx,” any number of optional contents may be registered. A private appwith nothing registered in a “control ID” of the public app managementtable 214 and the private app management table 215 to be described belowis excluded from control targets. That is, even when a public app isdeleted from the public app storage 211, a copied private app remainswithout disappearing from the private app storage 212.

Among the app usage controls, some controls may be used in combinationand others may not be used in combination. For example, “number oftimes” and “period” may be used in combination at the same time. At atime point when either one is reached first, deletion is performed. Acontrol target may not be limited to a public app. That is, the controlID may be set for not only a public app but also a private app. Forexample, when the registrant of the “CON2” is Mr. B, and the control ID“CON2” is set for a private app for Mr. B, only Mr. B is affected duringa period when the private app is stored in the private app storage 212Bfor Mr. B. Mr. B may also copy (publish) the private app stored in theprivate app storage 212B, in the public app storage 211.

A private app may be deleted from the screen management table 216 of auser. Otherwise, the private app may exist on the screen managementtable 216, but an icon on a screen may be hidden (including a grey out).Although a display of an icon remains, a processing may not be performedeven when the icon is operated (a notification such as a beep sound maybe made).

The app usage control function may be turned to an invalid state (lockedstate). For example, when the usage condition is “use once,” an unlockedstate may be made from the beginning. This is to perform counting in asituation “used 0 times” at a time point of copy so that after a copiedapp is used “once,” the app usage control will be executed. Adversely, alocked state is made when a trial period is set to a certain extent.During the trial period, the copied app may be used many times. Then,when a time “usable only once afterwards” comes, an unlocked state ismade. At this time point, counting of the number of times of use isstarted. In many “numbers of times” or “periods,” the usage would bemade in an unlocked state.

Configuration of Public App Management Table

FIG. 3 is a view illustrating an example of the public app managementtable 214. The public app management table 214 includes items such as a“management ID” that indicates a management number in the correspondingtable 214, an “app name” in which an application name is registered, a“UID” in which a unique identifier (UID) that uniquely identifies anapplication in the image forming apparatus 1 is registered, a“publisher” in which a person who has published the application isregistered, and a “control ID” in which the control ID of FIG. 2 isregistered. The [xxx] in the item of the “control ID” indicates a lockedstate. The [CON2] described in FIG. 3 indicates that CON2 is placed in alocked state. It is assumed that, in the “app name” described in FIG. 3,for example, “two copies” and “send to Mr. C” are registered.

Configuration of Private App Management Table

FIG. 4A is a view illustrating an example of the private app managementtable 215A for Mr. A. The private app management table 215A includesitems such as a “management ID” that indicates a management number inthe corresponding table 215A, an “app name” in which an application nameis registered, a “private UID” in which a private UID that uniquelyidentifies a private application in the private app storage 212A isregistered, and a “public UID” in which a UID that uniquely identifiesan application in the image forming apparatus 1 is registered. It isassumed that in the “app name” described in FIG. 4A, for example, “copyin black/white” and “two copies” are registered.

FIG. 4B is a view illustrating an example of the private app managementtable 215B for Mr. B. Similarly to the private app management table 215Afor Mr. A. The private app management table 215B includes items such asa “management ID,” an “app name,” a “private UID,” and a “public UID.”It is assumed that in the “app name” described in FIG. 4B, for example,“send to Mr. A” and “send to Mr. C in color” are registered.

Configuration of Screen Management Table

FIG. 5A is a view illustrating an example of the screen management table216A for Mr. A. The screen management table 216A is used for managing ascreen displayed on the operation display 22 when Mr. A logs in. Thescreen management table 216A includes items such as a “management ID”that indicates a management number in the corresponding table 216A, an“app name” in which an application name is registered, a “private UID”in which a private UID that uniquely identifies a private application inthe private app storage 212A is registered, a “public UID” in which aUID for uniquely identifying an application in the image formingapparatus 1 is registered, and a “control ID” described in FIG. 2. It isassumed that in the “app name” described in FIG. 5A, for example, “copyin black/white,” “two copies,” and “send to Mr. C” are registered.

In the private app storage 212A for Mr. A, the private apps of “copy inblack/white” and “two copies” are stored, but the private app of “sendto Mr. C” is not stored. However, the public app of “send to Mr. C”stored in the public app storage 211 may be registered in the screenmanagement table 216A for Mr. A so that a corresponding icon 101 c maybe displayed on a menu screen 100 a illustrated in FIG. 6A to bedescribed later, and the public app of “send to Mr. C” may be used.

FIG. 5B is a view illustrating an example of the screen management table216B for Mr. B. The screen management table 216B is used for managing ascreen displayed on the operation display 22 when Mr. B logs in.Similarly to FIG. 5A, the screen management table 216B includes itemssuch as a “management ID,” an “app name,” a “private UID,” a “publicUID,” and a “control ID.” It is assumed that in the “app name” describedin FIG. 5B, for example, “send to Mr. A,” “two copies,” and “send to Mr.C in color” are registered. The app name “send to Mr. C in color”indicates a private app that is created by duplicating the public app of“send to Mr. C” and changing setting values, but is given the samepublic UID as that of the original “send to Mr. C” and managed. Then,when the public app of “send to Mr. C” is deleted, not only the privateapp of “send to Mr. C,” but also the private app of “send to Mr. C incolor” whose app name is changed by changing setting values after copymay also be deleted.

In the private app storage 212B for Mr. B, the private apps of “send toMr. A” and “send to Mr. C in color” are stored, but the private app of“two copies” is not stored. However, the public app of “two copies”stored in the public app storage 211 may be registered in the screenmanagement table 216B for Mr. B so that a corresponding icon 101 b maybe displayed on a menu screen 100 b illustrated in FIG. 6B to bedescribed herein below, and the public app of “two copies” may be used.

Configuration of Menu Screen

FIG. 6A is a view illustrating an example of a menu screen displayed onthe operation display 22 when Mr. A logs in, and FIG. 6B is a viewillustrating an example of a menu screen displayed on the operationdisplay 22 when Mr. B logs in.

When Mr. A logs in, the menu screen 100 a displayed on the operationdisplay 22 is controlled by the display controller 204 based on thescreen management table 216A for Mr. A. When Mr. A logs in, the menuscreen 100 a includes, for example, respective icons 101 a, 101 b, and101 c of “copy in black/white,” “two copies,” and “send to Mr. C,” an“execute” button 102 by which an application corresponding to theselected icon 101 a to 101 c is executed, and a “cancel” button 103 thatcancels selection of the icon 101 a to 101 c, as illustrated in FIG. 6A.

As illustrated in FIG. 5A, nothing is set to the control ID of “send toMr. C.” Thus, when an administrator deletes the public app of “send toMr. C” from the public app storage 211, the icon 101 c of “send to Mr.C” is deleted from the menu screen 100 a. “Copy in black/white” is setwith the control ID “CON4,” and thus as illustrated in FIG. 2, Mr. A mayuse the private app of “copy in black/white” until 2018/3/31. That is,the icon 101 a of “copy in black/white” is deleted from the menu screen100 a after 2018/3/31.

When Mr. B logs in, the menu screen 100 b displayed on the operationdisplay 22 is controlled by the display controller 204 based on thescreen management table 216B for Mr. B. When Mr. B logs in, the menuscreen 100 b includes, for example, respective icons 101 d, 101 b, and101 e of “send to Mr. A,” “two copies,” and “send to Mr. C in color,” an“execute” button 102 by which an application corresponding to theselected icon 101 b, 101 d, or 101 e is executed, and a “cancel” button103 that cancels selection of the icon 101 b, 101 d, or 101 e, asillustrated in FIG. 6B. The “execute” button 102, and the “cancel”button 103 may not be provided.

As illustrated in FIG. 5B, “two copies” is not a copied one, and thus,nothing is set to the control ID related to the public UID “PPP1.” Then,even when an administrator deletes the public app of “two copies” fromthe public app storage 211, the icon 101 b of “two copies” does notdisappear from the menu screen 100 b. Also, even when Mr. B operates theicon 101 b of “two copies,” the icon 101 b is not operated because thereis no entity. The public app “send to Mr. C in color” is set with thecontrol ID “CON3,” and thus, as illustrated in FIG. 2, Mr. B may use theprivate app of “send to Mr. C in color” until 2018/12/1. That is, theicon 101 e of “send to Mr. C in color” is deleted from the menu screen100 b after 2018/12/1.

When a control ID set for a public app and a control ID set for aprivate app conflict with each other, either one, for example, thecontrol ID set for the private app, may be prioritized. Otherwise,either one may be deleted when used first. For example, when “use threetimes” is set for a public app, and “use once” is set for a private app,in the case of one use, “use once” for the private app is run anddeleted. When a control ID is not set for a public app, and a control IDis set for a private app, the control ID set for the private app mayfunction. When a control ID is not set for a private app, and a controlID is set for a public app, the control ID set for the public app mayfunction.

Hereinafter, respective units 200 to 205 of the controller 20 will bedescribed.

The receiving unit 200 accepts an operation on the operation display 22by an administrator or a user. When the administrator or the user inputsa user ID by operating the operation display 22, the receiving unit 200recognizes who has performed the operation based on the input user ID.

The first creating unit 201 creates a public application based on theoperation on the operation display 22 by the administrator.

The second creating unit 202 creates a private application based on theoperation on the operation display 22 by the administrator or the user.

When a public application is deleted from the public app storage 211,the deleting unit 203 deletes a corresponding private application fromthe private app storage 212 according to predetermined conditions.

The conditions include, for example, the following:

(1) the number of times a private app is usable or a period during whichthe private app is usable

(2) when either the number of times or the period in (1) is reachedfirst.

A condition may be determined for each user, or each private app. Forthe condition, validation or invalidation may be set for each user oreach private app. The condition may fail to start being used when thecondition is invalidated.

The deleting unit 203 may invalidate the function of an icon thatinstructs a private application to run on a display screen displayed toa corresponding user without deleting the private application stored inthe private app storage 212. In this case, the icon in which thefunction is invalidated may be hidden.

The display controller 204 performs a control such that a screenaccording to a user is displayed on the operation display 22, based onthe screen management table 216.

The execution unit 205 executes, with respect to a selected application,a processing specified by setting values held in the application bycontrolling, for example, the image reading unit 23, the image formingunit 24, and the communication unit 25.

Operation of Exemplary Embodiment

Hereinafter, an example of an operation of the image forming apparatus 1will be described.

(1) Creation of Public Application

FIG. 7 is a flowchart illustrating an example of a creation flow of apublic application.

The receiving unit 200 receives a user ID and a password through anoperation on the operation display 22 by an administrator (e.g., Mr. Z).When the received user ID and password are authenticated as belonging tothe administrator by the controller 20, the receiving unit 200 receivessetting items required for creating a public app and values of thecorresponding setting items (setting values) through an operation on theoperation display 22 by the administrator. The first creating unit 201creates the public app based on the setting items and the setting valuesreceived by the receiving unit 200, and stores the public app in thepublic app storage 211 (S1). The first creating unit 201 assigns a UIDto the created public app, and registers the UID together with an appname in the public app management table 214 illustrated in FIG. 3. Theapp name is given from the administrator through an operation on theoperation display 22.

The receiving unit 200 determines whether an app usage control has beendesignated for the created public app (S2). Designating an app usagecontrol for the public app is performed by inputting a correspondingcontrol ID to the operation display 22 by the administrator.

When it is determined that the app usage control has been designated (S2“Yes”), the receiving unit 200 assigns the input control ID to thepublic app (S3). That is, the control ID is registered in the public appmanagement table 214 illustrated in FIG. 3. Here, when the app usagecontrol is a new one, the control ID is also registered in the app usecontrol table 213 illustrated in FIG. 2.

Next, the receiving unit 200 determines whether a lock has beendesignated for the app usage control (S4). When it is determined thatthe lock has been designated for the app usage control (S4 “Yes”), thereceiving unit 200 gives a square bracket to the control ID of thepublic app management table 214 to lock the app usage control (S5). In acase where the lock of the app usage control is designated, theadministrator inputs information indicating the lock as well wheninputting the corresponding control ID to the operation display 22.

(2) Copy of Public Application

FIG. 8 is a flowchart illustrating an example of a copy flow of a publicapplication; Hereinafter, descriptions will be made on a case where auser performs a copy operation.

The receiving unit 200 receives a user ID and a password through anoperation on the operation display 22 by a user (e.g., Mr. A). When thereceived user ID and password are authenticated as belonging to Mr. A bythe controller 20, the receiving unit 200 receives selection of a publicapp as a copy target among public apps stored in the public app storage211 through an operation on the operation display 22 by Mr. A. Thesecond creating unit 202 copies the public app to create a private app,and stores the private app in the private app storage 212A for Mr. A.Then, the second creating unit 202 newly generates a private UID andregisters the private UID in the private app management table 215A forMr. A (S11).

The receiving unit 200 determines whether designation of an app usagecontrol for the copied private app has been received (S12).

When it is determined that the designation of the app usage control hasbeen received (S12 “Yes”), a control ID corresponding to the receivedapp usage control is given to the private app (S13). Here, when the appusage control is a new one, the control ID is registered in the app usecontrol table 213 illustrated in FIG. 2.

(3) Deletion of Public Application

FIG. 9 is a flowchart illustrating an example of a deletion flow of apublic application.

The receiving unit 200 receives a public app as a deletion target froman administrator after the authentication as described above. Thedeleting unit 203 determines whether an app usage control has beendesignated for the public app as the deletion target with reference tothe public app management table 214 (S21).

When it is determined that the app usage control is designated (S21:“Yes”), the deleting unit 203 executes the app usage control (S22).

The deleting unit 203 determines whether the public app is copied as aprivate app with reference to the public app management table 214 andthe private app management table 215 (S23).

When it is determined that the public app is copied as a private app(S23 “Yes”), the app usage control is unlocked with respect to eachprivate app (S24).

(4) Use of Private Application of Each User

FIG. 10 is a flowchart illustrating an example of a use flow of aprivate application of each user.

The execution unit 205 determines whether an unlocked app usage controlhas been designated for a public app, with reference to the private appmanagement table 215 (S31).

When it is determined that the app usage control has been designated(S31 “Yes”), the unlocked app usage control for the public app isexecuted (S32).

In step S31, when it is determined that the app usage control has notbeen designated (S31 “No”), it is determined whether an app usagecontrol for a private app is placed in an execution state (S33).

When it is determined that the app usage control for the private app isplaced in the execution state (S33 “Yes”), the app usage control isexecuted for the private app (S34).

First Modification

FIGS. 11A to 11C are views illustrating an example of an icon displayedon a display screen of the operation display 22 in the firstmodification. When a public app is copied and a private app is created,an icon that activates the private app is created, and is displayed onthe display screen of the operation display 22. In this case, the iconthat activates the private app may be displayed in a different manner soas to be distinguishable from an icon that activates the correspondingpublic app. For example, as illustrated in FIG. 11A, with respect to anicon 10 that activates the public app, an icon 11 that activates theprivate app may be displayed in a different color from the icon 10. Asillustrated in FIG. 11B, a control badge 12 may be added to the icon 11.As illustrated in FIG. 11C, in order to indicate that the icon 11 isplaced in a usable state (active state), “ON” may be added to an appname.

Second Modification

FIGS. 12A and 12B illustrate another example of the app use controltable 213 in a second modification. FIG. 12A is a view illustrating anexample of an app use control table 213 a, and FIG. 12B is a viewillustrating an example of a permission table.

As in FIG. 2, the app use control table 213 a illustrated in FIG. 12Aincludes items of a “control ID,” a “usage condition,” and a“registrant.”

A permission table 213 b illustrated in FIG. 12B includes items such asa “management ID” that indicates a management number in thecorresponding table 213 b, and a “permitted user” in which a permitteduser name is registered.

The conditions may include contents that permit a specific user to makeunlimited use. That is, when an app usage control of “CON10” is executed(unlocked), since the usage condition is “available if registered in apermission table,” for Mr. A, who is not registered in the permissiontable 213 b, a use is not permitted, and a private app is deleted fromthe private app storage 212A for Mr. A. Meanwhile, for Mr. B, who isregistered in the permission table 213 b, a use is permitted, and aprivate app is not deleted from the private app storage 212B for Mr. B.When an app usage control of “CON11” is executed (unlocked), since theusage condition is “available for Mr. A and Mr. B,” although notregistered in the permission table 213 b, Mr. A and Mr. B are allowed touse the app. By performing designation in this manner, it is possible tonarrow down the number of users permitted to perform copy.

Third Modification

FIG. 13 is a view illustrating another example of the app use controltable 213 in a third modification. The app use control table 213 cillustrated in the drawing includes items such as a “control ID,” a“usage condition,” and a “registrant” as in FIG. 2.

The conditions may include contents of an operation at the time ofdeletion. That is, the operation contents may include displaying awarning or displaying a screen for confirming continued use to enablethe continued use. Specifically, as in “CON20,” the usage condition maybe “use while stored in the public app storage, and warn each user about‘deleted’,” or as in “CON21,” the usage condition may be “use whilestored in the public app storage, and display ‘continue to use?’ toallow each user to select a subsequent use.”

Fourth Modification

FIGS. 14A to 14D are views for explaining another example of the publicapp management table 214 in a fourth modification. As illustrated inFIG. 14A, when the contents of the management ID“3” in the screenmanagement table 216B for Mr. B in FIG. 5B are registered in the publicapp management table 214 in FIG. 3 and developed as a public app, asillustrated in FIG. 14B, it is required to further designate a controlID that belongs to XXX. Here, since an app usage control assigned to anapp stored in the private app storage 212B for Mr. B needs to bemaintained, the public app management table 214 needs to be set asillustrated in FIG. 14C. When a UID PPP3 is deleted, an app usagecontrol of PPP2 and an app usage control of PPP3 are checked. FIG. 14Cindicates that the UID PPP3 refers to a public UID PPP2, and when acontrol ID of PPP2 is changed, PPP3 is automatically affected as well.In the case of FIG. 14C, control IDs [CON2], CON5, and CON3 are assignedto the UID PPP3.

For the case where this has been copied, as illustrated in FIG. 14D, itis desirable to have plural public UIDs.

As described above, an exemplary embodiment of the present disclosurehas been described. However, an exemplary embodiment of the presentdisclosure is not limited to the above-described exemplary embodiment,and may be modified and implemented in various ways within the scope inwhich the gist of the present disclosure is not changed. For example, inthe above exemplary embodiment, applications are stored in the storage21 of the image forming apparatus 1, but may be stored in an externalserver such as a cloud server. In the above exemplary embodiment, anapplication holds setting values, but the application may refer to thesetting values.

Each part or all of the respective units of the controller 20 may beconstituted by hardware circuits such as a reconfigurable circuit (FPGA:field programmable gate array) and an application specific integratedcircuit (ASIC).

Within the scope in which the gist of the present disclosure is notchanged, a part of constituent elements of the above exemplaryembodiment may be omitted or changed. Within the scope in which the gistof the present disclosure is not changed, in the flow of the aboveexemplary embodiment, it is possible to perform, for example, addition,deletion, modification, or change of a step. A program used in the aboveexemplary embodiment may be provided while recorded in acomputer-readable recording medium such as a CD-ROM. A program used inthe above exemplary embodiment may be stored in an external server suchas a cloud server, and then, used via a network.

Summary of Exemplary Embodiment

An information processing apparatus according to a further exemplaryembodiment of the present disclosure includes: a creating unit thatcreates, from a first application capable of executing a processingspecified by a setting value of registered setting items, a secondapplication for each user in such a manner that the second applicationis usable only by the user; a first receiving unit that receives, foreach setting item for the first application, designation of a typerelated to whether to change a setting value of the second application;a second receiving unit that receives change of a setting value for thesecond application; and a changing unit that changes, according to thetype, a setting value received by the second receiving unit.

The first application and the second application execute processingsspecified according to setting values of registered setting items. Asthe first application and the second application, for example, someapplications are immediately executed without displaying of a screen forconfirming setting values, and other applications are executed after ascreen for confirming setting values is displayed and confirmed.

The information processing apparatus may be, for example, an imageforming apparatus such as a multifunction machine or a facsimile device,a multifunctional mobile phone (smart phone), a personal computer (PC),or a tablet terminal.

Exemplary Embodiment

FIG. 15 is a block diagram illustrating an example of a control systemof an image forming apparatus according to another exemplary embodimentof the present disclosure. The image forming apparatus 1 is amultifunction machine having plural functions such as, for example,scanning, printing, copying, e-mailing, or facsimiling. The imageforming apparatus 1 includes a controller 20, a storage 21, an operationdisplay 22, an image reading unit 23, an image forming unit 24, and acommunication unit 25. The multifunction machine is an example of aninformation processing apparatus.

The controller 20 is constituted by, for example, a central processingunit (CPU) and an interface. The CPU operates in accordance with aninformation processing program 210 to function as a first receiving unit301, a second receiving unit 302, a first creating unit 201, a secondcreating unit 202, a changing unit 304, or an execution unit 205.Details of each of the units 301 to 205 will be described below.

The storage 21 is constituted by a read only memory (ROM), a randomaccess memory (RAM), or a hard disk, and stores various types ofinformation including the information processing program 210, a publicapp storage 211, and private app storages 212A and 212B, . . .(hereinafter, these may be collectively referred to as the “private appstorage 212”) provided for each user. In FIG. 15, it is assumed that theprivate app storage 212A is prepared for Mr. A as a user, and theprivate app storage 212B is prepared for Mr. B as a user. The user is anexample of a user excluding an administrator. Hereinafter, when both theadministrator and the user are included, the administrator and the userare also called operators.

The public app storage 211 stores a public application (hereinafter,also simply referred to as a “public app”) 51. The public application 51is an example of a first application.

The private app storage 212 stores a private application (hereinafter,also simply referred to as a “private app”) 52. The private application52 is an example of a second application. Hereinafter, the public app 51and the private app 52 may be collectively simply referred to as“applications.”

The public application 51 is an application published by a creator(hereinafter, referred to as an “administrator”) of the application, andonly the administrator has an authority to change setting values. Theprivate application 52 is an application obtained by duplicating thepublic application by an administrator or a user, which is not open toothers than the corresponding user. Only the corresponding user has anauthority to change setting values. In the present specification, “copy”indicates that the private application 52 is created while settingvalues held in the public application 51 are kept as they are.

An application of the exemplary embodiment holds setting informationincluding, for example, setting items and setting values in advance. Forexample, as applications, some applications may be immediately executedby a direct activation mode, in which a screen for confirming settingvalues is not displayed. Other applications may be executed after ascreen for confirming setting values is displayed and confirmed. Suchapplications include, for example, “two copies,” “send to Mr. A,” and“send to Mr. C in color.” The application “two copies” is an applicationby which two copies of a document with one or more pages are made. Theapp name “send to Mr. A” indicates an application by which an image issent to a user terminal device of Mr. A via an e-mail. The app name“send to Mr. C in color” indicates an application by which a color imageis sent to a user terminal device of Mr. C via an e-mail.

The operation display 22 has a touch panel display having a touch panelsuperimposed on a display portion such as a liquid crystal display,which displays a screen such as a menu screen on the display portion,and accepts an operation from an operator to the touch panel. On themenu screen, for example, an icon including an app name such as “twocopies” or “send to Mr. A” is displayed. When an icon is selected, thecorresponding application starts to run. The icon refers to arepresentation that shows, with a picture, a pictogram, a letter, or thelike, the function of processing executable by an application andinstructs execution of the processing.

The image reading unit 23 includes an automatic document feeder providedon a document table, and a scanner that reads image data from a documentplaced on the document table, or a document fed by the automaticdocument feeder. The image reading unit 23 stores the read image data inthe storage 21.

The image forming unit 24 forms a black-white image or a color image ona recording medium such as a sheet through, for example, anelectrophotographic system or an inkjet method.

The communication unit 25 transmits and receives data to/from anexternal device such as an administrator terminal device used by anadministrator and a user terminal device used by a user via a network,by an e-mail or a facsimile. The network is a communication network suchas a local area network (LAN), the Internet, or a public network, whichtransmits and receives data through, for example, a wired communicationor a wireless communication.

FIGS. 16A to 16C are views for explaining setting information held inapplications. FIG. 16A is a view illustrating an example of settinginformation before setting values of the public app 51 are changed, FIG.16B is a view illustrating an example of setting information after thesetting values of the public app 51 are changed, and FIG. 16C is a viewillustrating an example of setting information of the private app 52.Setting information 51 a of the public app 51, as illustrated in FIGS.16A and 16B, includes items such as “setting item” in which settingitems are recorded, “setting value” in which setting values arererecorded, and “type” in which the types of setting items are recorded.Setting information 52 a of the private app 52, as illustrated in FIG.16C, includes not only “setting item,” “setting value,” and “type” butalso “scheduled changed value” in which a setting value changed andscheduled is recorded. Examples of the “type” include “changeable,”“sustainably changeable,” and “unchangeable” types. These “types” arenon-limiting. For example, there may be only two types “changeable” and“unchangeable,” or another type may be added to “changeable,”“sustainably changeable,” and “unchangeable.”

Value setting may include “changeable setting” in which setting may bechanged by user authority for the created private app and “unchangeablesetting” in which setting may not be changed by user authority for thecreated private app and user authority of the public app serving as abasis is required.

Setting items included in the changeable setting may include, forexample, “changeable” and “sustainably changeable.” In the “changeable,”a user may arbitrarily change a setting value of the private app 52, andin the “sustainably changeable,” a user may keep a changed value of asetting value of the private app 52 by the user's intention.

Setting items included in the unchangeable setting may include, forexample, “unchangeable” and “confirmation of whether to change.” In the“unchangeable,” a user may not change a setting value of the private app52, and in the “confirmation of whether to change,” when a user of theprivate app wants to change a setting value, it is checked whether auser of the public app allows a setting change. In the exemplaryembodiment, a type of a confirmation of whether to change is notprovided, but may be provided.

That is, the “sustainably changeable” is a setting item in which anadministrator may change a setting value of the private app 52 when auser's consent is obtained. The “unchangeable” is a setting item inwhich an administrator may forcibly change a setting value of theprivate app 52.

It is assumed that an administrator has changed setting values a1, b1,and c1 of setting items A, B, and C in the public app illustrated inFIG. 16A, to setting values a2, b2, and c2, respectively, as illustratedin FIG. 16B. The changing unit 304 to be described below, as illustratedin FIG. 16C, writes setting values a2 and b2 in the items of “scheduledchanged value,” with the types of “sustainably changeable” and“unchangeable” in the private app 52.

Hereinafter, each of units 301 to 205 of the controller 20 will bedescribed.

The first receiving unit 301 accepts an operation of an administrator onthe operation display 22. Specifically, the first receiving unit 301receives, from the administrator, for example, designation of the typeof a setting item for each setting item, change of a setting value ofthe public app 51, and a scheduled changed value, which is a settingvalue of the private app 52 changed and scheduled. The type of thesetting item relates to whether to change a setting value of the privateapp 52. The type of the setting item may include, for example,“changeable,” “sustainably changeable,” and “unchangeable.” It isassumed that a setting item not designated with any type is designatedwith a type of “changeable,” “sustainably changeable” or “unchangeable.”

The second receiving unit 302 accepts an operation of a user on theoperation display 22. Specifically, the second receiving unit 302receives change of a setting value of the private app 52. In the casewhere the type of a setting item is not “changeable,” when the privateapp 52 is selected, the second receiving unit 302 notifies the user of ascheduled changed value at the next use of the private app 52 by thecorresponding user.

In the case where the type of a setting item is “sustainablychangeable,” when the private app 52 is selected, the second receivingunit 302 displays a screen for confirming whether to accept change of ascheduled changed value, on the operation display 22, even though thecorresponding private app 52 is an application immediately executedwithout displaying of a screen for confirming setting contents.

The first creating unit 201 creates the public app 51 based on theoperation by the administrator on the operation display 22 of the imageforming apparatus 1. The first creating unit 201 also creates an iconcorresponding to the public app in order to display the icon on the menuscreen.

The second creating unit 202 creates the private app 52 for each userfrom the public app 51, based on the operation by the administrator orthe user on the operation display 22 of the image forming apparatus 1.The second creating unit 202 copies setting values of the public app 51at the time of creation of the private app 52, and newly stores thesetting values. The second creating unit 202 also creates an iconcorresponding to the private app 52 in order to display the icon on themenu screen.

The changing unit 304 changes the setting value received by the secondreceiving unit 302 according to the type of the setting item. In thecase where the type of the setting item is “unchangeable” or“sustainably changeable,” and the change of the scheduled changed valueis accepted by the user, when the private app 52 is selected, thechanging unit 304 changes the setting value to the scheduled changedvalue.

The execution unit 205 executes, with respect to a selected application,a processing specified by setting values held in the application bycontrolling, for example, the image reading unit 23, the image formingunit 24, and the communication unit 25.

Operation of Exemplary Embodiment

Hereinafter, an example of an operation of the image forming apparatus 1will be described.

(1) Creation of Public App and Private App

FIG. 17 is a flowchart illustrating an example of a creation flow of apublic app and a private app.

An administrator operates the operation display 22 of the image formingapparatus 1 to input his user ID and password. After the authentication,the administrator operates the operation display 22 to designate settingitems required for creating a public app and values of the correspondingsetting items (setting values). The first receiving unit 301 receivesthe designated setting items and setting values (S1).

The administrator operates the operation display 22 to designate a typerelated to whether to change a setting value in the private app 52, withrespect to each of the setting items. The first receiving unit 301receives the designated type for each of the setting items (S2).

When the first receiving unit 301 receives an instruction to create anapp from the administrator (S3), the first creating unit 201 creates thepublic app 51 that holds the setting information 51 a including thesetting items, the setting values and the types received by the firstreceiving unit 301 (S4). The first creating unit 201 stores the createdpublic app 51 in the public app storage 211.

Next, through an operation of the administrator or the user, the secondcreating unit 202 copies the public app 51 stored in the public appstorage 211 to create the private app 52 for each user. The secondcreating unit 202 stores the created private app 52 in each private appstorage 212. Accordingly, each user may access his private app storage212 and use the private app 52. In this step, each of the setting valuesin each private app 52 is the same as that in the public app 51.

(2) Change of Setting Value of Setting Item in Private App

FIG. 18 is a flowchart illustrating an example of flow of change of asetting value of the private app.

The user operates the operation display 22 to designate a setting itemhaving a setting value he wants to change, among setting items set forthe private app 52. The second receiving unit 302 receives thedesignated setting item, and determines whether the type of the settingitem is “changeable” with reference to the setting information 52 a ofthe private app 52 (S11).

When it is determined that the type is “changeable” (S11 “Yes”), thesecond receiving unit 302 receives change of the setting value by theuser (S12). The changing unit 304 rewrites and replaces the settingvalue held by the private app 52 with the received setting value (S13).

In step S11, when it is determined that the type of the designatedsetting item is not “changeable” (S11 “No”), the processing ends.

(3) Change of Setting Value of Public App

FIG. 19 is a flowchart illustrating an example of a flow of change of asetting value of the public app.

The administrator operates the operation display 22 of the image formingapparatus 1 to input his user ID and password. After the authentication,the administrator operates the operation display 22 to designate asetting item and input a changed setting value. The first receiving unit301 receives the input setting value, and the changing unit 304 rewritesthe setting value of the public app 51, with the received setting value.The changing unit 304 records the setting value changed in the publicapp 51, in the “scheduled changed value” of the private app 52 (S20).

The changing unit 304 determines whether the type of the setting itemfor which the scheduled changed value is recorded is “changeable,” withreference to the setting information 52 a of the private app 52 (S21).

When it is determined that the type is “changeable” (S21 “Yes”), theprocessing ends.

When it is determined that the type is not “changeable,” that is,“unchangeable” or “sustainably changeable” (S21 “No”), the changing unit304 determines whether the setting value of the public app 51 is thesame as the setting value of the private app 52 with respect to thecorresponding setting item (S22).

When it is determined that both are not the same (S22 “No”), the settingvalue of the public app 51 is recorded in the “scheduled changed value”of the private app 52 (S23). For example, it is assumed that the publicapp (for example, an app name “send to Mr. A”) 51 by which an image issent to a user terminal device of Mr. A is created. In this case, sincethere is a possibility that a mail address of Mr. A may be changed, thetype is set as “unchangeable.” When the mail address of Mr. A ischanged, by inputting the changed mail address, it is possible to writethe changed mail address in the public app 51 of “send to Mr. A,” as thescheduled changed value.

When it is determined that both are the same (S22 “Yes”), the scheduledchanged value is deleted from the setting information 52 a of theprivate app 52 (S24).

(4) At Activation of private app after setting value of public app ischanged

FIG. 20 is a flowchart illustrating an example of a flow at the time ofactivation of the private app after a setting value of the public app ischanged.

The user selects an icon from the menu screen by operating the operationdisplay 22, and activates the private app 52 stored in the private appstorage 212 allocated to the user himself/herself. Then, the changingunit 304 determines whether there is a setting item having a settingvalue recorded in the “scheduled changed value,” with reference to thesetting information 52 a of the private app 52 (S31). When it isdetermined that the scheduled changed value is recorded (S31 “Yes”), thechanging unit 304 determines whether the type of the correspondingsetting item is “sustainably changeable” (S32).

When it is determined that the type of the setting item is “sustainablychangeable” (S32 “Yes”), the fact that the setting value has changed isnotified to the user (S33).

In the private app 52, a confirmation screen as to whether to acceptchange of the setting value is displayed on the operation display 22 sothat the user performs confirmation (S34). When the user expresses anintention to accept the change of the setting value, for example, whenthe user operates a “YES” button on the confirmation screen (S34 “Yes”),the changing unit 304 rewrites the setting value of the private app 52with the value of the “scheduled changed value” (S35). Instead of the“YES” button on the confirmation screen, an input of voice, for example,“Yes” may be used. Alternatively, an operation on a smartphone or anoperation of putting hands over may be used.

The changing unit 304 deletes the value of the “scheduled changed value”(S36).

The changing unit 304 displays the confirmation screen of settingcontents including setting items and setting values on the operationdisplay 22 (S37).

When the user operates a “start” button on the confirmation screen(S38), the execution unit 205 activates the private app 52 (S39).Accordingly, the job is activated.

In step S32, when it is determined that the type of the setting item is“unchangeable” (S32 “No”), the fact that the setting value has changedis notified to the user (S40).

Thereafter, as described above, the processings in steps S35 to S39 areperformed.

In step S31, when it is determined that the scheduled changed value isnot recorded in the setting item (S31 “No”), it is determined whether amode is a direct activation mode (S41). When it is determined that themode is a direct activation mode (S41 “Yes”), the job is activated(S39).

When it is determined that the mode is not a direct activation mode (S41“No”), the job is activated (S39) through display of the confirmationscreen (S37) and an operation of the “start” button (S38).

First Modification

In a case where there exists a third private app created from a secondprivate app, and the second and third private apps are created by thesame creator, when the third private app is selected under acircumstance where setting values of the second private app were notchanged at the time when the second private app was selected, the secondreceiving unit 302 may be configured not to display the screen for theconfirmation.

Second Modification

In a case where there exists a third private app created from a secondprivate app, and the second and third private apps are created bydifferent creators, when the third private app is selected under acircumstance where setting values of the second private app were notchanged at the time when the second private app was selected, the secondreceiving unit 302 may display the screen for the confirmation such thatthe setting values are changeable.

As described above, an exemplary embodiment of the present disclosurehas been described. However, an exemplary embodiment of the presentdisclosure is not limited to the above-described exemplary embodiment,and may be modified and implemented in various ways within the scope inwhich the gist of the present disclosure is not changed. For example, inthe above exemplary embodiment, a public app and a private app arestored in the storage 21 within the image forming apparatus 1, but maybe stored in an external server such as a cloud server. In the aboveexemplary embodiment, an application holds setting values, but theapplication may refer to the setting values.

The applications used in the above exemplary embodiment hold settinginformation, but may refer to setting values, types, and scheduledchanged values.

Each part or all of the respective units of the controller 20 may beconstituted by hardware circuits such as a reconfigurable circuit (FPGA:field programmable gate array) and an application specific integratedcircuit (ASIC).

Within the scope in which the gist of the present disclosure is notchanged, a part of constituent elements of the above exemplaryembodiment may be omitted or changed. Within the scope in which the gistof the present disclosure is not changed, in the flow of the aboveexemplary embodiment, it is possible to perform, for example, addition,deletion, modification, or change of a step. A program used in the aboveexemplary embodiment may be provided while recorded in acomputer-readable recording medium such as a CD-ROM. A program used inthe above exemplary embodiment may be stored in an external server suchas a cloud server, and then, used via a network.

The foregoing description of the exemplary embodiments of the presentinvention has been provided for the purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Obviously, many modificationsand variations will be apparent to practitioners skilled in the art. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, therebyenabling others skilled in the art to understand the invention forvarious embodiments and with the various modifications as are suited tothe particular use contemplated. It is intended that the scope of theinvention be defined by the following claims and their equivalents.

What is claimed is:
 1. An information processing apparatus comprising: acreating unit that creates, from a first application deletable by aperson with a first authority, a second application deletable by aperson with a second authority; and a deleting unit that deletes thesecond application according to a predetermined condition when the firstapplication is deleted.
 2. The information processing apparatusaccording to claim 1, wherein the condition includes the number of timesthe second application is usable or a period during which the secondapplication is usable.
 3. The information processing apparatus accordingto claim 2, wherein the condition includes a case where either of thenumber of times or the period is reached first.
 4. The informationprocessing apparatus according to claim 1, wherein the condition isdetermined for each person with the second authority.
 5. The informationprocessing apparatus according to claim 4, wherein the condition permitsa specific person with the second authority to make unlimited use. 6.The information processing apparatus according to claim 1, wherein thecondition is determined for each second application.
 7. The informationprocessing apparatus according to claim 2, wherein the condition allowsvalidation or invalidation to be set for each person with the secondauthority or each second application, and when the invalidation is set,the condition does not start being used.
 8. The information processingapparatus according to claim 1, wherein the condition includes contentsof an operation for the deletion.
 9. The information processingapparatus according to claim 8, wherein the contents of the operationinclude displaying a warning or displaying a screen for confirmingcontinued use to enable the continued use.
 10. The informationprocessing apparatus according to claim 1, wherein the deleting unitdeletes the second application from a storage area that stores thesecond application.
 11. The information processing apparatus accordingto claim 1, wherein without deleting the second application stored in astorage area, the deleting unit invalidates a function of an instructionunit that instructs the second application to run on a display screendisplayed to the person with the second authority.
 12. The informationprocessing apparatus according to claim 11, wherein the invalidatedinstruction unit is hidden.
 13. The information processing apparatusaccording to claim 1, wherein the creating unit copies setting values ofthe first application when the second application is created, and newlystores the setting values.
 14. An information processing apparatuscomprising: a creating unit that creates, from a first applicationcapable of executing a processing specified by a setting value ofregistered setting items, a second application for each user in such amanner that the second application is usable only by the user; a firstreceiving unit that receives, for each setting item for the firstapplication, designation of a type related to whether to change asetting value of the second application; a second receiving unit thatreceives change of a setting value for the second application; and achanging unit that changes, according to the type, a setting valuereceived by the second receiving unit.
 15. The information processingapparatus according to claim 14, wherein when the type is not changeableand the second application is selected, the second receiving unitnotifies the user of a scheduled changed value that is scheduled to beused for change of a setting value of the first application at next timewhen the user uses the second application.
 16. The informationprocessing apparatus according to claim 15, wherein when the type is asustainably changeable type and the second application is selected, thesecond receiving unit displays a screen for confirming whether to acceptchange of the scheduled changed value even if the second application isan application to be immediately executed without display of a screenfor confirming setting contents.
 17. The information processingapparatus according to claim 14, wherein when the type is anunchangeable type and the second application is selected, the changingunit changes a setting value to a scheduled changed value.
 18. Theinformation processing apparatus according to claim 14, wherein thefirst receiving unit receives designation of the type from a creator ofthe first application.
 19. The information processing apparatusaccording to claim 18, wherein the first receiving unit receives, fromthe creator of the first application, a scheduled changed value that isscheduled to be used for change of a setting value of the firstapplication.
 20. The information processing apparatus according to claim19, wherein the receiving unit records the scheduled changed value inthe second application when setting values of the first and secondapplications are different from each other.
 21. The informationprocessing apparatus according to claim 14, wherein when the secondapplication is created, the creating unit copies a setting value of thefirst application and newly stores the setting value.
 22. Theinformation processing apparatus according to claim 14, wherein thesecond receiving unit does not display a screen for confirmation when athird application created from the second application exists, the secondand third applications are created by the same creator, and the thirdapplication is selected under a circumstance where no setting value ischanged upon selection of the second application.
 23. The informationprocessing apparatus according to claim 14, wherein the second receivingunit displays a screen for confirmation to enable change of a settingvalue when a third application created from the second applicationexists, the second and third applications are created by differentcreators, and the third application is selected.